Skip to content

docs: add migration guide from 3 to 4 - #288

Closed
korvin89 wants to merge 1 commit into
mainfrom
docs/migration-3-to-4
Closed

docs: add migration guide from 3 to 4#288
korvin89 wants to merge 1 commit into
mainfrom
docs/migration-3-to-4

Conversation

@korvin89

Copy link
Copy Markdown
Contributor

Summary

  • add migration notes for 3.x -> 4.x
  • document the main breaking behavior changes for RelativeDateField, DateField/RangeDateField, and Calendar selection styling
  • link the new guide from the main README

@korvin89
korvin89 requested review from ValeraS and amje as code owners July 30, 2026 13:39
@gravity-ui-bot

Copy link
Copy Markdown
Contributor

Preview is ready.

@github-actions

Copy link
Copy Markdown

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 66.51% 1726 / 2595
🔵 Statements 66.67% 1761 / 2641
🔵 Functions 70.4% 345 / 490
🔵 Branches 60.78% 1418 / 2333
File CoverageNo changed files found.
Generated in workflow #106 for commit ebdb5f9 by the Vitest Coverage Report Action

@gravity-ui-bot

Copy link
Copy Markdown
Contributor

🎭 Tests Report is ready.
🎭 Coverage Report is ready.

Comment thread docs/migration-3-to-4.md
Comment on lines +44 to +48
const handleUpdate = (value) => {
if (value !== null) {
setState(value);
}
};

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A strange proposal. This approach doesn't allow empty fields and doesn't rely on real-time updates. THe component doesn't support live updates any more.

Comment thread docs/migration-3-to-4.md
Comment on lines +85 to +89
const handleBlur = () => {
if (currentValueRef.current) {
saveValue(currentValueRef.current);
}
};

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

???

Comment thread docs/migration-3-to-4.md
## Migration checklist

- Review handlers that depend on `onUpdate` during typing.
- Make sure your form logic handles “invalid/incomplete intermediate input” without assuming it is committed.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an incorrect statement. The user didn't receive an invalid/incomplete value, but rather a null value immediately after the input became invalid. Now, they receive the null value only after they finish editing the input.

@korvin89 korvin89 closed this Aug 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants